Facilitating the resolution of address conflicts in a networked media playback system

ABSTRACT

Examples are disclosed and described to facilitate resolution of Internet Protocol address conflicts. An example method includes listening, by a first playback device having a first IP address, to a specified server port, receiving, by the first playback device from a second playback device via the specified server port, a message, wherein the message identifies a second IP address, wherein the second IP address has been assigned to the second playback device, determining, by the first playback device, whether the first IP address is the same as the second IP address, and when the first IP address is the same as the second IP address, obtaining, by the first playback device, a new IP address, wherein the new IP address is different from the first IP address and the second IP address.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other items directedto media playback or some aspect thereof.

BACKGROUND

Digital music has become readily available due in part to thedevelopment of consumer level technology that has allowed people tolisten to digital music on a personal audio device. The consumer'sincreasing preference for digital audio has also resulted in theintegration of personal audio devices into PDAs, cellular phones, andother mobile devices. The portability of these mobile devices hasenabled people to take the music listening experience with them andoutside of the home. People have become able to consume digital music,like digital music files or even Internet radio, in the home through theuse of their computer or similar devices. Now there are many differentways to consume digital music, in addition to other digital contentincluding digital video and photos, stimulated in many ways byhigh-speed Internet access at home, mobile broadband Internet access,and the consumer's hunger for digital media.

Until recently, options for accessing and listening to digital audio inan out-loud setting were severely limited. In 2005, Sonos offered forsale its first digital audio system that enabled people to, among manyother things, access virtually unlimited sources of audio via one ormore networked connected zone players, dynamically group or ungroup zoneplayers upon command, wirelessly send the audio over a local networkamongst zone players, and play the digital audio out loud in synchrony.The Sonos system can be controlled by software applications downloadedto certain network capable, mobile devices and computers.

Given the insatiable appetite of consumers towards digital media, therecontinues to be a need to develop consumer technology thatrevolutionizes the way people access and consume digital media.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example network for media content playback;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 9 shows an internal functional block diagram of the example passiveresolver of FIG. 4;

FIG. 10 shows an internal functional block diagram of the example activeresolver of FIG. 4;

FIG. 11 shows an illustrative flowchart for an example method forresolving IP address conflicts;

FIGS. 12a and 12b show illustrative flow paths for resolving IP addressconflicts in an example environment;

FIG. 13 shows an illustrative flowchart for another example method forresolving IP address conflicts;

FIG. 14 shows an illustrative flowchart for another example method forresolving IP address conflicts;

FIGS. 15a and 15b show illustrative flow paths for resolving IP addressconflicts in another example environment;

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the inventions are not limited tothe arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments disclosed herein enable resolving conflicts of addresses(such as an Internet Protocol (IP) address) in a networked mediaplayback system. In some embodiments, a network includes an access pointand at least a first playback device of a media playback system. In someembodiments, the first playback device in the network monitors data sentto the access point from playback devices in the network. In someembodiments, when data sent to the access point includes a request for anew IP address, the first playback device determines whether the IPaddress included in the request is the same as the IP address currentlyassigned to the first playback device. That is, the first playbackdevice monitors the network to determine if any other playback device(s)in the network is requesting an IP address that conflicts with the firstplayback device IP address. In some embodiments, when the first playbackdevice makes an IP address conflict determination, the first playbackdevice requests a new IP address form the access point to facilitateresolution of the IP address conflict.

In some embodiments, the first playback device monitors the network forevents indicative of a status change of the access point. In someembodiments, when the first playback device detects a change in statusof the access point, the first playback device obtains a new IP addressfrom the access point. Unlike prior systems, embodiments disclosedherein enable the first playback device to alert other playbackdevice(s) in the network to obtain new IP addresses. To this end, insome embodiments, the first playback device periodically broadcastsprobe messages over the network to the other playback devices. When astatus change is detected, in some embodiments, the first playbackdevice sets an IP address renew flag in a subsequent probe message. Insome embodiments, when another playback device obtains a probe messagewith an IP address renew flag set, the playback device obtains a new IPaddress from the access point.

Other embodiments, as those discussed in the following and others as canbe appreciated by one having ordinary skill in the art are alsopossible.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media systemconfiguration 100 in which one or more embodiments disclosed herein canbe practiced or implemented.

By way of illustration, the media system configuration 100 is associatedwith a home having multiple zones, though the home could have beenconfigured with only one zone. Additionally, one or more zones can beadded over time. Each zone may be assigned by a user to a different roomor space, such as, for example, an office, bathroom, bedroom, kitchen,dining room, family room, home theater room, utility or laundry room,and patio. A single zone might also include multiple rooms or spaces ifso configured. With respect to FIG. 1, one or more of zone players102-124 are shown in each respective zone. A zone player 102-124, alsoreferred to herein as a playback device, multimedia unit, speaker,player, and so on, provides audio, video, and/or audiovisual output. Acontroller 130 (e.g., shown in the kitchen for purposes of thisillustration) provides control to the media system configuration 100.Controller 130 may be fixed to a zone, or alternatively, mobile suchthat it can be moved about the zones. The media system configuration 100may also include more than one controller 130, and additionalcontrollers may be added to the system over time.

The media system configuration 100 illustrates an example whole housemedia system, though it is understood that the technology describedherein is not limited to, among other things, its particular place ofapplication or to an expansive system like a whole house media systemconfiguration 100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, 204 of FIGS. 2A, 2B, and 2C, respectively, can correspond toany of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200, 202, 204 may also bereferred to as a “smart speaker,” because they contain processingcapabilities beyond the reproduction of audio, more of which isdescribed below.

FIG. 2A illustrates zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 may bedynamically configured to reproduce a subset of full-range sound, suchas when zone player 200 is grouped with other zone players to playstereophonic audio, monaural audio, and/or surround audio or when theaudio content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a particular zone player in a zone or zone group may beassigned to a playback queue (or “queue”). The playback queue containsinformation corresponding to zero or more audio items for playback bythe associated zone or zone group. The playback queue may be stored inmemory on a zone player or some other designated device. Each itemcontained in the playback queue may comprise a uniform resourceidentifier (URI) or some other identifier that can be used by the zoneplayer(s) to seek out and/or retrieve the audio items from theidentified audio source(s). Depending on the item, the audio sourcemight be found on the Internet (e.g., the cloud), locally from anotherdevice over a data network 128 (described further below), from thecontroller 130, stored on the zone player itself, or from an audiosource communicating directly to the zone player. In some embodiments,the zone player can reproduce the audio itself (e.g., play the audio),send the audio to another zone player for reproduction, or both wherethe audio is reproduced by the zone player as well as one or moreadditional zone players (possibly in synchrony). In some embodiments,the zone player may play a first audio content (or alternatively, maynot play the content at all), while sending a second, different audiocontent to another zone player(s) for reproduction. To the user, eachitem in a playback queue is represented on an interface of a controllerby an element such as a track name, album name, playlist, or some otherrepresentation. A user can populate the playback queue with audio itemsof interest. The user may also modify and clear the playback queue, ifso desired.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present,and/or future zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player mayinclude or interact with a docking station for an Apple IPOD™ or similardevice.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, the controller 300 may correspond to thecontrolling device 130 of FIG. 1. Docking station 302, if provided orused, may provide power to the controller 300 and additionally maycharge a battery of the controller 300. In some embodiments, thecontroller 300 may be provided with a touch screen 304 that allows auser to interact through touch with the controller 300, for example, toretrieve and navigate a playlist of audio items, control operations ofone or more zone players, and provide overall control of the mediasystem configuration 100. In other embodiments, other input mechanismssuch as voice control may be used to interact with the controller 300.In certain embodiments, any number of controllers can be used to controlthe media system configuration 100. In some embodiments, there may be alimit set on the number of controllers that can control the media systemconfiguration 100. The controllers might be wireless like the wirelesscontroller 300 or wired to the data network 128.

In some embodiments, if more than one controller is used in the mediasystem configuration 100 of FIG. 1, each controller may be coordinatedto display common content, and may all be dynamically updated toindicate changes made to the media system configuration 100 from asingle controller. Coordination can occur, for instance, by a controllerperiodically requesting a state variable directly or indirectly from oneor more of the zone players. For example, the state variable may provideinformation about the media system configuration 100, such as currentzone group configuration, what is playing in one or more zones, volumelevels, and other items of interest. The state variable may be passedaround on the data network 128 between zone players (and controllers, ifso desired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an IPHONE™, IPAD™, ANDROID™ powered phone or tablet, orany other smart phone or network-enabled device can be used as thecontroller 130 in the example media system configuration 100. Anapplication running on a laptop or desktop personal computer (PC) orMac™ can also be used as the controller 130. Such controllers mayconnect to the media system configuration 100 through an interface withthe data network 128, a zone player, a wireless router, or using someother configured connection path. Example controllers offered by Sonos,Inc. of Santa Barbara, Calif. include a “Controller 200,” “SONOS®CONTROL,” “SONOS® Controller for IPHONE™,” “SONOS® Controller forIPAD™,” “SONOS® Controller for ANDROID™,” “SONOS® Controller for MAC™ orPC.”

c. Example Data Connection

The zone players 102 to 124 of FIG. 1 are coupled directly or indirectlyto a data network, such as the data network 128. The example controller130 may also be coupled directly or indirectly to the data network 128or individual zone players. The data network 128 is represented by anoctagon in the figure to stand out from other representative components.While the data network 128 is shown in a single location, it isunderstood that such a network is distributed in and around the mediasystem configuration 100. Particularly, the data network 128 can be awired network, a wireless network, or a combination of both wired andwireless networks. In some embodiments, one or more of the zone players102-124 are wirelessly coupled to the data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers are coupled to the data network 128 using a centralized accesspoint such as a wired or wireless router. In some embodiments, one ormore of the zone players 102-124 are coupled via a wire to the datanetwork 128 using Ethernet or similar technology. In addition to the oneor more zone players 102-124 connecting to the data network 128, thedata network 128 can further allow access to a wide area network, suchas the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create the datanetwork 128. Other zone players 102-124 can then be added wired orwirelessly to the data network 128. For example, a zone player (e.g.,any of zone players 102-124) can be added to the media systemconfiguration 100 by simply pressing a button on the zone player itself(or perform some other action), which enables a connection to be made tothe data network 128. The broadband router can be connected to anInternet Service Provider (ISP), for example. The broadband router canbe used to form another data network within the media systemconfiguration 100, which can be used in other applications (e.g., websurfing). The data network 128 can also be used in other applications,if so programmed. An example, second network may implement SONOSNET™protocol, developed by SONOS, Inc. of Santa Barbara. SONOSNET™represents a secure, AES-encrypted, peer-to-peer wireless mesh network.Alternatively, in certain embodiments, the data network 128 is the samenetwork, such as a traditional wired or wireless network, used for otherapplications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106, 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via the controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with the controller130. Moreover, in some embodiments, zone configurations may bedynamically changed even after being configured using the controller 130or some other mechanism.

In some embodiments, a “bonded zone” contains two or more zone players,such as the two zone players 106, 108 in the family room, whereby thetwo zone players 106, 108 can be configured to play the same audiosource in synchrony. In one example, the two zone players 106, 108 canbe paired to play two separate sounds in left and right channels, forexample. In other words, the stereo effects of a sound can be reproducedor enhanced through the two zone players 106, 108, one for the leftsound and the other for the right sound. In another example, two or morezone players can be sonically consolidated to form a single,consolidated zone player. A consolidated zone player (though made up ofmultiple, separate devices) can be configured to process and reproducesound differently than an unconsolidated zone player or zone playersthat are paired, because a consolidated zone player has additionalspeaker drivers from which sound can be passed. The consolidated zoneplayer can further be paired with a single zone player or yet anotherconsolidated zone player. Each playback device of a consolidatedplayback device can be set in a consolidated mode, for example.

In certain embodiments, paired or consolidated zone players (alsoreferred to as “bonded zone players”) can play audio in synchrony withother zone players in the same or different zones.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing the controller 130, and not by physically connecting andre-connecting speaker wire, for example, to individual, discretespeakers to create different configurations. As such, certainembodiments described herein provide a more flexible and dynamicplatform through which sound reproduction can be offered to theend-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via the zone player 124, while someone is preparing food in thekitchen and listening to classical music via the zone player 102.Further, someone can be in the office listening to the same jazz musicvia the zone player 110 that is playing on the patio via the zone player124. In some embodiments, the jazz music played via the zone players110, 124 is played in synchrony. Synchronizing playback amongst zonesallows for someone to pass through zones while seamlessly (orsubstantially seamlessly) listening to the audio. Further, zones can beput into a “party mode” such that all associated zones will play audioin synchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, audio on a zone player itself may beaccessed and played. In some embodiments, audio on a controller may beaccessed via the data network 128 and played. In some embodiments, musicfrom a personal library stored on a computer or networked-attachedstorage (NAS) may be accessed via the data network 128 and played. Insome embodiments, Internet radio stations, shows, and podcasts may beaccessed via the data network 128 and played. Music or cloud servicesthat let a user stream and/or download music and audio content may beaccessed via the data network 128 and played. Further, music may beobtained from traditional sources, such as a turntable or CD player, viaa line-in connection to a zone player, for example. Audio content mayalso be accessed using a different protocol, such as AIRPLAY™, which isa wireless technology by Apple, Inc., for example. Audio contentreceived from one or more sources can be shared amongst the zone players102 to 124 via the data network 128 and/or the controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 may be shared with any of the zoneplayers 102-124 in the media system configuration 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, a speaker unit 418 coupled to the audio amplifier 416, anaddress resolver 422, an IP leaser 428 and a database 430. In theillustrated example of FIG. 4, the database 430 includes stateinformation about the zone player 400. For example, the database 430 mayinclude the currently assigned internet protocol (IP) address of thezone player 400, the media access control (MAC) address of the zoneplayer 400, which (if any) other zone players the zone player 400 is incommunication with, whether the zone player 400 is to forward messagesreceived at the zone player 400 to other zone players, etc. FIG. 2Ashows an example illustration of such a zone player. Other types of zoneplayers may not include the speaker unit 418 (e.g., such as shown inFIG. 2B) or the audio amplifier 416 (e.g., such as shown in FIG. 2C).Further, it is contemplated that the zone player 400 can be integratedinto another component. For example, the zone player 400 could beconstructed as part of a television, lighting, or some other device forindoor or outdoor use.

In some embodiments, the network interface 402 facilitates a data flowbetween the zone player 400 and other devices on the data network 128.In some embodiments, in addition to getting audio from another zoneplayer or device on the data network 128, the zone player 400 may accessaudio directly from the audio source, such as over a wide area networkor on the local network. In some embodiments, the network interface 402can further handle the address part of each packet so that it gets tothe right destination or intercepts packets destined for the zone player400. Accordingly, in certain embodiments, each of the packets includesan Internet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, the network interface 402 can include one or bothof a wireless interface 404 and a wired interface 406. The wirelessinterface 404, also referred to as a radio frequency (RF) interface,provides network interface functions for the zone player 400 towirelessly communicate with other devices (e.g., other zone player(s),speaker(s), receiver(s), component(s) associated with the data network128, and so on) in accordance with a communication protocol (e.g., anywireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.11ad, 802.15, 4G mobile communication standard, and soon). The wireless interface 404 may include one or more radios. Toreceive wireless signals and to provide the wireless signals to thewireless interface 404 and to transmit wireless signals, the zone player400 includes one or more antennas 420. The wired interface 406 providesnetwork interface functions for the zone player 400 to communicate overa wire with other devices in accordance with a communication protocol(e.g., IEEE 802.3). In some embodiments, a zone player includes multiplewireless 404 interfaces. In some embodiments, a zone player includesmultiple wired 406 interfaces. In some embodiments, a zone playerincludes both of the interfaces 404 and 406. In some embodiments, a zoneplayer 400 includes only the wireless interface 404 or the wiredinterface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in the memory 410. The memory 410 is data storagethat can be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part of theprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for playback throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom the zone player 400, send to another zone player on a network, orboth play and send to another zone player on the network. An exampleinput includes a line-in connection (e.g., an auto-detecting 3.5 mmaudio line-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5™, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

In the illustrated example of FIG. 4, the example zone player 400includes the example address resolver 422 to facilitate resolution ofinternet protocol (IP) address conflicts that may occur in a network(e.g., the example data network 128 (FIG. 1)). For example, two or morezone players in the data network 128 may use the same IP address. In theillustrated example, the zone player 400 of FIG. 4 includes a passiveresolver 424 and an active resolver 426.

In the illustrated example of FIG. 4, the example passive resolver 424monitors the data network 128 to determine when a new IP address isassigned to a device (e.g., the zone player 400) in the data network128. For example, the passive resolver 424 may monitor an access point(e.g., a wired router, a wireless router, etc.) to detect when theaccess point assigns a device in the data network 128 a new IP address.For example, the passive resolver 424 may “listen” to an input port ofthe access point, such as a server port (e.g., a user datagram protocol(UDP) server port 67), and identify when the access point obtains arequest packet from another zone player. The example passive resolver424 may then compare an IP address included in the request packet withits own IP address and determine whether an IP address conflict exists.For example, the passive resolver 424 may retrieve the currentlyassigned IP address of the zone player 400 from the example database 430and compare it to the IP address included in the request packet. In someembodiments, the passive resolver 424 may initiate the example IP leaser428 to renew the IP address of the zone player 400 in response to an IPaddress conflict. In some embodiments, the passive resolver 424 mayinitiate renewing the IP address of the zone player 400 in response todetecting that the access point obtained a request packet.

In the illustrated example of FIG. 4, the example active resolver 426monitors the power status of a wired connection to an access point todetermine when the zone player 400 is to renew its IP address or tolease a new IP address. For example, the active resolver 426 may monitorthe power status (e.g., power ON, power OFF) of the example wiredinterface 406 of the example network interface 402. In response todetecting a change in power status (e.g., power OFF to power ON), theexample active resolver 426 of FIG. 4 initiates the example IP leaser428 to renew the IP address of the zone player 400 or to lease a new IPaddress. In some embodiments, the example active resolver 426 propagatesthe change in power status of the wired interface 406 to (if any) otherzone players in the same network as the zone player 400. For example,the active resolver 426 may periodically (e.g., every thirty minutes)and/or aperiodically (e.g., in response to a detected power statuschange) broadcast probe messages to other zone players in the exampledata network 128. Probe messages may include a message identifier (e.g.,a 16-bit number) identifying the probe message, a zone player identifier(e.g., a MAC address) of the zone player broadcasting the probe message,a forwarding flag indicative of whether a zone player that obtains theprobe message is to forward the probe message, and a renew IP flagindicative of whether the zone player that obtains the probe message isto renew its IP address in response to processing the probe message.

In the illustrated example of FIG. 4, the example zone player 400includes the example IP leaser 428 to renew IP addresses when initiatedor to lease a new IP address. The example IP leaser 428 may be initiatedwhen the zone player 400 is rebooted (e.g., the IP leaser 428 is tolease a new IP address), when a currently leased IP address is expiring(e.g., the IP leaser 428 is to renew its currently leased (or assigned)IP address), in response to a message from the passive resolver 424, inresponse to a message from the active resolver 424, etc. That is, theexample IP leaser 428 may be initiated when the zone player 400 is in abind state, in a renew state and/or in a discover state. In theillustrated example of FIG. 4, the example IP leaser 428 uses thedynamic host configuration protocol (DHCP) when communicating with ahost (e.g., a DHCP server such as an access point).

In the illustrated example, the IP leaser 428 generates and unicasts arequest message to the access point to renew its IP lease. For example,the IP leaser 428 may send a DHCP_REQUEST packet to the access pointwhen the currently leased IP address lease is expiring and/or when theexample address resolver 422 detects the access point rebooting. Whenthe access point accepts the request to renew the IP address, the accesspoint returns an IP address renewal message (e.g., a DHCP_ACK packet) tothe IP leaser 428. Otherwise, when the access point denies the requestto renew the IP address, the access point returns a negativeacknowledgement message (e.g., a DHCP_NACK packet) to the IP leaser 428.For example, when the access point is rebooted, the access point maylose IP address binding information for the one or more zone playersleasing IP addresses from the access point. Thus, the access point isunable to renew any IP address lease.

In some embodiments, in response to receiving a negative acknowledgementmessage from the access point, the IP leaser 428 initiates a new bindingprocess. For example, the IP leaser 428 may broadcast discover message(e.g., a DHCP_DISCOVER packet) on the example data network 128 toidentify all available DHCP servers. In some embodiments, the IP leaser428 obtains an offer message for an IP address lease. For example, aDHCP server (e.g., an access point) may unicast to the IP leaser 428 orbroadcast over the data network 128 a response message (e.g., aDHCP_OFFER packet) offering an IP address lease to the IP leaser 428.The offer message may include an IP address and a lease duration. Insome embodiments, the example IP leaser 428 responds to the offermessage by broadcasting a request message (e.g., a DHCP_REQUEST packet).For example, the IP leaser 428 may request the offered IP address fromthe access point. The request message includes the IP address offered.For example, the offered IP address may be included in a “Your IPAddress” (YIPADDR) field (e.g., an options field) of the requestmessage. In some embodiments, the example IP leaser 428 configures theexample network interface 402 with the IP address lease information(e.g., the IP address, the lease duration, the DHCP server accepting theIP address lease, etc.) in response to an acknowledgement message (e.g.,a DHCP_ACK packet) obtained by the IP leaser 428. For example, theaccess point may unicast to the IP leaser 428 or broadcast over the datanetwork 128 the acknowledgement message when the access point acceptsthe binding request (e.g., request to lease an IP address). The exampleIP leaser 428 may then store the leased IP address in the exampledatabase 430. In some embodiments, the access point determines whetherto unicast or broadcast a message based on a broadcast flag included ina message obtained from a client (e.g., the zone player 400). Forexample, if the broadcast flag (e.g., a bit) is set (e.g., one, on, yes,true, etc.), the access point broadcasts its response message over thedata network 128. Otherwise, if the broadcast flag is not set (e.g.,zero, off, no, false, etc.), the access point unicasts its responsemessage to the client. In some examples, the access point may send anaddress resolution protocol (ARP) packet first.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram for acontroller 500, which can correspond to the controlling device 130 inFIG. 1. The controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, 4G mobile communicationstandard, and so on). Further, when a particular audio is being accessedvia the controller 500 or being played via a zone player, a picture(e.g., album art) or any other data, associated with the audio and/oraudio source can be transmitted from a zone player or other electronicdevice to the controller 500 for display.

The example controller 500 is provided with a screen 502 and an inputinterface 514 that allows a user to interact with the controller 500,for example, to navigate a playlist of many multimedia items and tocontrol operations of one or more zone players. The screen 502 on thecontroller 500 can be an LCD screen, for example. The screen 502communicates with and is commanded by a screen driver 504 that iscontrolled by a microcontroller 506 (e.g., a processor). A memory 510can be loaded with one or more application modules 512 that can beexecuted by the microcontroller 506 with or without a user input via auser interface 514 to achieve certain tasks. In some embodiments, anapplication module 512 is configured to facilitate grouping a number ofselected zone players into a zone group and synchronizing the zoneplayers for audio playback. In some embodiments, an application module512 is configured to control the audio sounds (e.g., volume) of the zoneplayers in a zone group. In operation, when the microcontroller 506executes one or more of the application modules 512, the screen driver504 generates control signals to drive the screen 502 to display anapplication specific user interface accordingly.

The controller 500 includes the network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as anIPHONE™, IPAD™ or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or MAC™) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup playback an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplayback is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zoneplayers, for example, by starting with a single zone and then manuallylinking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed or learned action. Other kinds of zone scenes can beprogrammed or learned by the system over time.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone can be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, and so on), a backup buzzer can be programmed to sound.The buzzer can include a sound file that is stored in a zone player, forexample.

V. Playback Queue

As discussed above, in some embodiments, a zone player may be assignedto or otherwise associated with a playback queue identifying zero ormore media items for playback by the zone player. The media itemsidentified in a playback queue may be represented to the user via aninterface on a controller. For instance, the representation may show theuser (or users if more than one controller is connected to the system)how the zone player is traversing the playback queue, such as byhighlighting the “now playing” item, graying out the previously playeditem(s), highlighting the to-be-played item(s), and so on.

In some embodiments, a single zone player is assigned to a playbackqueue. For example, the zone player 114 in the bathroom of FIG. 1 may belinked or assigned to a “Bathroom” playback queue. In an embodiment, the“Bathroom” playback queue might have been established by the system as aresult of the user naming the zone player 114 to the bathroom. As such,contents populated and identified in the “Bathroom” playback queue canbe played via the zone player 114 (the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playbackqueue. For example, zone players 106, 108 in the family room of FIG. 1may be linked or assigned to a “Family room” playback queue. In anotherexample, if family room and dining room zones were grouped, then the newgroup would be linked or assigned to or otherwise associated with a“family room+dining room” playback queue. In some embodiments, thefamily room+dining room playback queue may be established based upon thecreation of the group. In some embodiments, upon establishment of thenew group, the family room+dining room playback queue can automaticallyinclude the contents of one (or both) of the playback queues associatedwith either the family room or dining room or both. In one instance, ifthe user started with the family room and added the dining room, thenthe contents of the family room playback queue would become the contentsof the family room+dining room playback queue. In another instance, ifthe user started with the family room and added the dining room, thenthe family room playback queue would be renamed to the familyroom+dining room playback queue. If the new group was “ungrouped,” thenthe family room+dining room playback queue may be removed from thesystem and/or renamed to one of the zones (e.g., renamed to “familyroom” or “dining room”). After ungrouping, each of the family room andthe dining room will be assigned to a separate playback queue. One ormore of the zone players in the zone or zone group may store in memorythe associated playback queue.

As such, when zones or zone groups are “grouped” or “ungrouped”dynamically by the user via a controller, the system will, in someembodiments, establish or remove/rename playback queues respectively, aseach zone or zone group is to be assigned to a playback queue. In otherwords, the playback queue operates as a container that can be populatedwith media items for playback by the assigned zone. In some embodiments,the media items identified in a playback queue can be manipulated (e.g.,re-arranged, added to, deleted from, and so on).

By way of illustration, FIG. 6 shows an example network 600 for mediacontent playback. As shown, the example network 600 includes examplezone players 612, 614, example audio sources 662, 664, and example mediaitems 620. The example media items 620 may include playlist 622, musictrack 624, favorite Internet radio station 626, playlists 628, 630, andalbum 632. In one embodiment, the zone players 612, 614 may be any ofthe zone players shown in FIGS. 1, 2, and 4. For instance, zone players612, 614 may be the zone players 106, 108 in the Family Room.

In one example, the example audio sources 662, 664, and example mediaitems 620 may be partially stored on a cloud network, discussed morebelow in connection to FIG. 8. In some cases, the portions of the audiosources 662, 664, and example media items 620 may be stored locally onone or both of the zone players 612, 614. In one embodiment, playlist622, favorite Internet radio station 626, and playlist 630 may be storedlocally, and music track 624, playlist 628, and album 632 may be storedon the cloud network.

Each of the example media items 620 may be a list of media itemsplayable by a zone player(s). In one embodiment, the example media itemsmay be a collection of links or pointers (e.g., URI) to the underlyingdata for media items that are stored elsewhere, such as the audiosources 662, 664. In another embodiment, the media items may includepointers to media content stored on the local zone player, another zoneplayer over a local network, or a controller device connected to thelocal network.

As shown, the example network 600 may also include an example queue 602associated with the zone player 612, and an example queue 604 associatedwith the zone player 614. The playback queue 606 may be associated witha group, when in existence, comprising the zone player 612 and the zoneplayer 614. The playback queue 606 might comprise a new queue or existas a renamed version of the queue 602 or 604. In some embodiments, in agroup, the zone players 612, 614 would be assigned to the playback queue606, and the playback queues 602, 604 would not be available at thattime. In some embodiments, when the group is no longer in existence, theplayback queue 606 is no longer available. Each zone player and eachcombination of zone players in a network of zone players, such as thoseshown in FIG. 1 or that of the example zone players 612, 614, and theexample combination 616, may be uniquely assigned to a correspondingplayback queue.

A playback queue, such as the playback queues 602, 604, 606, may includeidentification of media content to be played by the corresponding zoneplayer or combination of zone players. As such, media items added to theplayback queue are to be played by the corresponding zone player orcombination of zone players. The zone player may be configured to playitems in the queue according to a specific order (such as an order inwhich the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and othermedia items added to the queue. In one embodiment, the items in theplayback queue 602 to be played by the zone player 612 may include itemsfrom the audio sources 662, 664, or any of the media items 622-632. Theplayback queue 602 may also include items stored locally on the zoneplayer 612, or items accessible from the zone player 614. For instance,the playback queue 602 may include the Internet radio 626 and the album632 items from the audio source 662, and items stored on the zone player612.

When a media item is added to the queue via an interface of acontroller, a link to the item may be added to the queue. In a case ofadding a playlist to the queue, links to the media items in the playlistmay be provided to the queue. For example, the playback queue 602 mayinclude pointers from the Internet radio 626 and the album 632, pointersto items on the audio source 662, and pointers to items on the zoneplayer 612. In another case, a link to the playlist, for example, ratherthan a link to the media items in the playlist may be provided to thequeue, and the zone player or combination of zone players may play themedia items in the playlist by accessing the media items via theplaylist. For example, the album 632 may include pointers to itemsstored on the audio source 662. Rather than adding links to the items onthe audio source 662, a link to the album 632 may be added to theplayback queue 602, such that the zone player 612 may play the items onthe audio source 662 by accessing the items via pointers in the playlist632.

In some cases, contents as they exist at a point in time within aplayback queue may be stored as a playlist, and subsequently added tothe same queue later or added to another queue. For example, contents ofthe playback queue 602, at a particular point in time, may be saved as aplaylist, stored locally on the zone player 612 and/or on the cloudnetwork. The saved playlist may then be added to the playback queue 604to be played by the zone player 614.

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 todescribe, for purposes of illustration, certain embodiments to provideand facilitate connection to a playback network. FIG. 7 shows that thereare three zone players 702, 704 and 706 and a controller 708 that form anetwork branch that is also referred to as an Ad-Hoc network 710. Thenetwork 710 may be wireless, wired, or a combination of wired andwireless technologies. In general, an Ad-Hoc (or “spontaneous”) networkis a local area network or other small network in which there isgenerally no one access point for all traffic. With an establishedAd-Hoc network 710, the devices 702, 704, 706, 708 can all communicatewith each other in a “peer-to-peer” style of communication, for example.Furthermore, devices may join and/or leave from the network 710, and thenetwork 710 will automatically reconfigure itself without needing theuser to reconfigure the network 710. While an Ad-Hoc network isreferenced in FIG. 7, it is understood that a playback network may bebased on a type of network that is completely or partially differentfrom an Ad-Hoc network.

Using the Ad-Hoc network 710, the devices 702, 704, 706, 708 can shareor exchange one or more audio sources and be dynamically grouped (orungrouped) to play the same or different audio sources. For example, thedevices 702, 704 are grouped to playback one piece of music, and at thesame time, the device 706 plays back another piece of music. In otherwords, the devices 702, 704, 706, 708, as shown in FIG. 7, form aHOUSEHOLD that distributes audio and/or reproduces sound. As usedherein, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked devices that are cooperating to provide an application orservice. An instance of a HOUSEHOLD is identified with a household 710(or household identifier), though a HOUSEHOLD may be identified with adifferent area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 710 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., securitykeys). In an embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 708) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 708 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 706 in FIG. 7 is shown to be connected to bothnetworks, for example. The connectivity to the network 712 is based onEthernet and/or Wireless, while the connectivity to other devices 702,704, 708 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player706, 704, 702 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, thezone player 702 may contain a uniform resource locator (URL) thatspecifies an address to a particular audio track in the cloud. Using theURL, the zone player 702 may retrieve the audio track from the cloud,and ultimately play the audio out of one or more zone players.

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnectednetworks including a cloud-based network and at least one local playbacknetwork. A local playback network includes a plurality of playbackdevices or players, though it is understood that the playback networkmay contain only one playback device. In certain embodiments, eachplayer has an ability to retrieve its content for playback. Control andcontent retrieval can be distributed or centralized, for example. Inputcan include streaming content provider input, third party applicationinput, mobile device input, user input, and/or other playback networkinput into the cloud for local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality ofcontent providers 820-850 can be connected to one or more local playbacknetworks 860-870 via a cloud and/or other network 810. Using the cloud810, a multimedia audio system server 820 (e.g., Sonos™), a mobiledevice 830, a third party application 840, a content provider 850 and soon can provide multimedia content (requested or otherwise) to localplayback networks 860, 870. Within each local playback network 860, 870,a controller 862, 872 and a playback device 864, 874 can be used toplayback audio content.

VIII. Example Resolution of Internet Protocol Address Conflicts

During operation, an access point (e.g., a wired and/or wireless router)enables playback devices such as zone players on a network tocommunicate on that network. The access point maintains an IP addressconfiguration in a data structure such as a lookup table, a list, adocument, etc. For example, the access point may identify an IP addressto lease (e.g., assign) to a device on the network based on available IPaddresses included in the IP address configuration. However, in someembodiments, when the access point is rebooted (or changes to the powerON state from the power OFF state), the IP address configuration storedin the data structure may be lost. For example, the IP addressconfiguration may be stored in temporary memory that resets when poweris removed to the memory.

In certain instances, such as, for example, those described above, an IPaddress conflict may develop in a network, whereby, for example, morethan one device on the network may use the same IP address. Duplicate IPaddresses may occur when, for example, the access point reboots.Duplicate IP address resolution is not defined for network devices thatare not in direct communication (e.g., directly connected via wired orwireless interface) to the access point. For example, the access pointmay be unaware that a first device is assigned a first IP address when asecond device requests a lease for the first IP address because the IPaddress configuration (e.g., data structure including available IPaddresses) was lost when the access point was rebooted. Accordingly,embodiments disclosed herein enable resolving IP address conflicts in anetwork.

FIG. 9 illustrates an example block diagram of the example passiveresolver 424 of the zone player depicted in FIG. 4. The example passiveresolver 424 of FIG. 9 monitors a data network to detect IP addresslease requests from other device(s) communicating on the network. Forexample, the passive resolver 424 may identify when another zone player(e.g., the example zone player 400 (FIG. 4), a laptop, a smart phone,etc. requests an IP address (either to renew its IP address or to bindto a new IP address) on a data network, such as the data network 128(FIG. 1), the ad-hoc network 710 (FIG. 7), the Sonos Network 1 860and/or Sonos Network N 870 (FIG. 8). The example passive resolver 424may then facilitate resolution of duplicate IP addresses by, forexample, requesting a new (or renewing an) IP address. The examplepassive resolver 424 of FIG. 9 includes an example server port monitor902 and an example request handler 904.

In the illustrated example of FIG. 9, the example passive resolver 424includes the example server port monitor 902 to monitor messages (e.g.,DHCP messages or packets) sent to a host (e.g., an access point) on anetwork such as the example data network 128 (FIG. 1). For example, theserver port monitor 902 may monitor user datagram protocol (UDP) serverport (67) and UDP client port (68). The UDP server port (67) is adestination port to send data to a server. That is, messages thatcommunicate via the UDP server port (67) correspond to messages sent toa host device such as an access point from a client device such as aplayback device. In contrast, the UDP client port (68) is a destinationport for data sent to a client. That is, messages that communicate viathe UDP client port (68) correspond to messages obtained by a clientdevice such as the zone player 400 (FIG. 4) from a host device. Thus,the example server port monitor 902 enables the example passive resolver424 to detect IP address lease request messages sent from another deviceon the network to an access point on the network. In some embodiments,the example server port monitor 902 monitors the UDP server port (67)while the zone player is in a bind state (e.g., the client device isconnected to a host device). In some embodiments, the example serverport monitor 902 monitors the UDP server port (67) while the zone playeris in a renew state (e.g., trying to renew the currently assigned IPaddress) or in the discover state (e.g., when the client device isinitiating a new binding process).

In the illustrated example of FIG. 9, the example passive resolver 424includes the example request handler 904 to determine whether the IPaddress included in an IP address lease request message is the same asthe IP address leased (e.g., currently assigned) to the zone player 400.For example, request handler 904 may retrieve the zone player 400 IPaddress from the example database 430 (FIG. 4) and compare it to the IPaddress included in the “YIPADDR” (e.g., Your IP Address) options fieldof the request message. In some embodiments, if the IP addresses do notmatch (e.g., are not the same or equivalent), the example requesthandler 904 discards the IP address lease request message. Otherwise, insome embodiments, if the IP addresses do match (e.g., are the same orequivalent), the example request handler 904 initiates the example IPleaser 428 (FIG. 4) to obtain a new IP address for the zone player 400.As discussed above in connection with the IP leaser 428, when the IPleaser 428 requests to renew an IP address, the IP leaser receives anegative acknowledgement message (e.g., a DHCP_NACK packet) because theIP address included in the renew request message is the same as the IPaddress of another device on the network.

In some embodiments, the example passive resolver 424 may not includethe example request handler 904. That is, in some embodiments, when theexample server port monitor 902 detects an IP address lease request, theexample server port monitor 902 may initiate the example IP leaser 428regardless of whether the IP address included in the request message isthe same as the IP address of the zone player 400.

FIG. 10 illustrates an example block diagram of the example activeresolver 426 of FIG. 4. The example active resolver 426 of FIG. 10monitors the power status of a wired connection to an access point in anetwork. For example, the active resolver 426 may monitor the wiredinterface 406 (FIG. 4) to detect a change in the power status. In someembodiments, a change in power status of the wired interface 406 isindicative of a change in power status (e.g., a reboot) of an accesspoint that is in communication with the wired interface 406. In someembodiments, the active resolver 426 may then request a new IP address(or request to renew the IP address already assigned (e.g., leased) tothe device) and cause other devices in communication with the activeresolver 426 and/or the access point to request new IP addresses (orrequest to renew the existing IP addresses). The example active resolver426 of FIG. 10 includes an example wired interface monitor 1002, anexample message generator 1004, an example probe handler 1006 and anexample renew handler 1008.

In the illustrated example of FIG. 10, the example wired interfacemonitor 1002 monitors power status changes in the wired interface of thezone player 400 (FIG. 4). For example, the wired interface monitor 1002may detect changes in the Ethernet status (e.g., “eth0”) of the wiredinterface 406. In some embodiments, the eth0 is a binary status bit thatindicates that the Ethernet status is either ON or OFF. In someembodiments, when the wired interface monitor 1002 detects a change inthe eth0 from the power OFF state to the power ON state, the examplewired interface monitor 1002 initiates the example IP leaser 428 (FIG.4) to initiate an IP address renew request or a new binding process. Forexample, the change in the eth0 may indicate that the access point wasrebooted. Accordingly, the example active resolver 426 initiates theexample IP leaser 428 to cause the access point to update available IPaddresses in the IP address configuration of the data network.

In the illustrated example of FIG. 10, the example message generator1004 generates probe messages that are broadcast by zone players on adata network, such as the data network 128 (FIG. 1), the ad-hoc network710 (FIG. 7), the Sonos Network 1 860 and/or Sonos Network N 870 (FIG.8). Probe messages may include a message identifier (e.g., a 16-bitnumber) identifying the probe message, a zone player identifier (e.g., aMAC address) of the zone player broadcasting the probe message, aforwarding flag indicative of whether a zone player that obtains theprobe message is to forward the probe message, and a renew IP flagindicative of whether the zone player that obtains the probe message isto renew its IP address in response to processing the probe message. Insome embodiments, the probe messages are broadcast periodically by thezone players on the data network. For example, a probe message may besent every 500 milliseconds. In some embodiments, the probe messages arebroadcast aperiodically by the zone players on the data network. Forexample, a zone player may send a probe message in response to adetected change in the eth0 status.

In some embodiments, the example message generator 1004 of FIG. 10generates a probe message with a new message identifier to identifydifferent probe messages. For example, the message identifier may be alocally generated sequence number such as a 16-bit number. In someembodiments, the active resolver 426 may use the message identifier todetermine whether the probe message was previously obtained. Forexample, a probe message may be forwarded from one zone player on thedata network to another zone player until the probe message is obtainedby a zone player for a second time. In the illustrated example, theexample message generator 1004 of FIG. 10 stores the new messageidentifier in the example database 430 (FIG. 4). In some embodiments,the example message generator 1004 of FIG. 10 includes a MAC address ofthe zone player that generates a probe message in the probe message.

In the illustrated example, the example message generator 1004 of FIG.10 updates the status of a renew IP flag included in the probe messagein response to determinations made by the example wired interfacemonitor 1002. For example, when the wired interface monitor 1002 detectsa change in the power status of the eth0, the example message generator1004 may set (e.g., one, yes, on, true, etc.) the renew IP flag. Whenthe example wired interface monitor 1002 does not detect a change in thepower status of the eth0, the example message generator may reset (e.g.,zero, no, off, false, etc.) the renew IP flag. The status of the renewIP flag may be used by the example probe handler 1006 to determinewhether the active resolver 426 is to initiate the example IP leaser428.

In the illustrated example of FIG. 10, the example active resolver 426includes the example probe handler 1006 to process probe messagesobtained by the active resolver 426 from another zone player. Forexample, the probe handler 1006 may periodically and/or aperiodicallyobtain a probe message from another zone player on a data network, suchas the data network 128 (FIG. 1), the ad-hoc network 710 (FIG. 7), theSonos Network 1 860 and/or Sonos Network N 870 (FIG. 8). In theillustrated example, the probe handler 1006 of FIG. 10 checks the statusof the renew IP flag of the probe message. In some embodiments, when therenew IP flag is set (e.g., one, yes, on, true, etc.), the example probehandler 1006 outputs a message indicative of the new probe message tothe example renew handler 1008.

In some embodiments, the example probe handler 1006 may determinewhether the renew IP flag of the probe message is to be reset in a probemessage based on a time-to-live for the renew IP flag. For example, aprobe message may include a timestamp indicative of when the examplemessage generator 1004 generated the probe message. In some suchembodiments, when the example probe handler 1006 obtains a probe messagewith a renew IP flag that is set, the example probe handler 1006 maydetermine whether the time-to-live of the renew IP flag expired based onthe timestamp included in the probe message. For example, thetime-to-live for a set renew IP flag may be equal to the round trippropagation delay through the network. Thus, the example probe handler1006 may check whether the set renew IP flag time-to-live (e.g., thedifference between the time the probe message is obtained and the timethe probe message is generated) is less than the round trip propagationdelay. Accordingly, the example probe handler 1006 forwards the probemessage to the example renew handler 1008 when the set renew IP flagtime-to-live has not expired, and discards the probe message if thetime-to-live has expired.

In some embodiments, the example probe handler 1006 may also check thestatus of the forwarding flag in the probe message to determine whetherthe probe message is to be forwarded to other zone players on the datanetwork. For example, the probe handler 1006 may forward the probemessage to the example message generator 1004 when the forwarding flagis set (e.g., one, yes, on, true, etc.) and may discard the probemessage when the forwarding flag is reset (e.g., zero, no, off, false,etc.).

In the illustrated example of FIG. 10, the example active resolver 426includes the example renew handler 1008 to determine whether theobtained probe message is a new probe message or a previously obtainedprobe message. For example, the renew handler 1008 may retrievepreviously obtained message identifiers from the example database 430 tocompare to the message identifier included in the probe message. If theprobe message is a new probe message (e.g., not previously obtained),the example renew handler 1008 initiates the example IP leaser 428 (FIG.4). Otherwise, the example renew handler 1008 may discard the probemessage.

In some embodiments, the renew handler 1008 may use hysteresis to avoidinitiating the example IP leaser 428 multiple times to request renewingthe IP address of the zone player. For example, the renew handler 1008may include a timer that starts each time the renew handler 1008initiates the example IP leaser 428. If another request to renew the IPaddress is obtained before the timer expires, the renew handler 1008 maydiscard the probe message. This may be useful when, for example,multiple eth0 status events are detected by the example wired interfacemonitor 1002. For example, a bad power connection may cause unwantedrapid eth0 status changes.

FIG. 11 shows an illustrative flowchart for an example method 1100 tofacilitate resolution of IP address conflicts, in accordance with atleast some embodiments described herein. For example, the example method1100 may use the example passive resolver 424 to facilitate resolutionof IP address conflicts. The example method 1100 of FIG. 11 begins atblock 1102 when the example passive resolver 424 (FIGS. 4 and/or 9)monitors messages sent to an access point on a data network, such as thedata network 128 (FIG. 1), the ad-hoc network 710 (FIG. 7), the SonosNetwork 1 860 and/or Sonos Network N 870 (FIG. 8). For example, theserver port monitor 902 (FIG. 9) may “listen” to messages sent to theUDP server port (67) from other devices (e.g., one or more zone players,one or more laptops, one or more smart phones, etc.). At block 1104, theexample passive resolver 424 determines whether a message sent to theaccess point includes an IP address lease renew request. For example,the server port monitor 902 checks whether the message sent to the UDPserver port (67) includes a DHCP_REQUEST packet. If the example serverport monitor 902 determines that the message does not include an IPaddress lease renew request at block 1104, then control proceeds toblock 1110 to determine whether to continue monitoring for IP addressconflicts.

Otherwise, if the example server port monitor 902 determines that themessage sent to the UDP server port (67) does include an IP addresslease renew request at block 1104, then, at block 1106, the examplepassive resolver 424 determines whether the IP address included in therequest message is a duplicate IP address. For example, the requesthandler 904 (FIG. 9) may retrieve the IP address of the zone player(e.g., the example zone player 400) from the example database 430 (FIG.4) to compare to the IP address included in the IP address lease renewrequest (e.g., the value of the “YIPADDR” options field of the request).If the example request handler 904 determines the request message is nota duplicate IP address at block 1106, then control proceeds to block1110 to determine whether to continue monitoring for IP addressconflicts.

Otherwise, if the example request handler 904 determines the requestmessage is a duplicate IP address at block 1106, then, at block 1108,the example passive resolver 424 requests a new IP address. For example,the request handler 904 may initiate the example IP leaser 428 (FIG. 4)to request an IP address lease renewal. At block 1110, the examplepassive resolver 424 determines whether to continue monitoring for IPaddress conflicts. If the passive resolver 424 determines to continuemonitoring for IP address conflicts, control returns to block 1102 tomonitor messages sent to the access point. Otherwise, if, at block 1110,the passive resolver 424 determines not to continue monitoring for IPaddress conflicts (e.g., due to an application/process shutdown event, ahardware shutdown event, etc.), the example method of FIG. 11 ends.

As an illustrative example, FIGS. 12a and 12b show example flow pathsfor resolving IP address conflicts in an example environment 1200 suchas the example media system configuration 100 (FIG. 1). The exampleenvironment 1200 includes an example access point 1202 (e.g., a wiredand/or wireless router), an example wired zone player 1204, and examplewireless zone players 1206, 1207. The example access point 1202, theexample wired zone player 1204 and the example wireless zone players1206, 1207 are in communication via an example data network 1208. Theexample wired zone player 1204 is in communication with the exampleaccess point 1202 via a wired interface (e.g., the example wiredinterface 406 (FIG. 4)). The example wireless zone players 1206, 1207are in communication with the example access point 1202 via a wirelessinterface (e.g., the example wireless interface 404 (FIG. 4)).

FIG. 12a is representative of the state of the example environment 1200after the access point 1202 reboots. Accordingly, the example accesspoint 1202 includes an IP address configuration 1210 that indicates allIP addresses on the example data network 1208 are available (e.g., arenot leased to any devices). Thus, the example access point 1202 isunaware that the example wireless zone player 1206 is leasing IP address1212 (e.g., 102.168.00.01) and that the example wireless zone player1207 is leasing IP address 1213 (e.g., 102.168.00.02). In addition, theexample wired zone player 1204 having detected the access point reboot,broadcasts an IP address lease renew request 1214 over the data network1208. However, because the IP address configuration 1210 does notinclude any IP address leasing information, the example access point1202 sends a negative acknowledgement message 1215 to the wired zoneplayer 1204. Accordingly, the example wired zone player 1204 of FIG. 12ahas no IP address 1216 (e.g., 0.0.0.0) and initiates a new bindingprocess 1218 over the data network 1208. During the binding process1218, the example wired zone player 1204 may broadcast a discovermessage (e.g., a DHCP_DISCOVER packet), and receive, in response to thediscover message, a DHCP_OFFER packet from the access point 1202. TheDHCP_OFFER packet may include an IP address offered to the wired zoneplayer 1204 (in this example IP address 1222 (e.g., 192.168.00.02)). Inresponse to the DHCP_OFFER packet, the example wired zone player 1204may broadcast a DHCP_REQUEST packet that includes the IP address 1222(e.g., 192.168.00.02).

FIG. 12b is representative of the state of the example environment 1200after the example access point 1202 leases the IP address 1222 to thewired zone player 1204. In response to the access point 1202 obtainingan IP address lease request message (e.g., the DHCP_REQUEST message)from the wired zone player 1204, the example wireless zone players 1206,1207 also detect the request message. For example, the wireless zoneplayers 1206, 1207 may include a passive resolver (e.g., the examplepassive resolver 424 (FIGS. 4 and/or 9)) that monitors the UDP serverport (67) for IP address lease request messages sent to the access point1202. In the illustrated example, the passive resolver of the wirelesszone player 1206 may determine that duplicate IP addresses do not exist.For example, the wireless zone player 1206 may compare its IP address1212 (e.g., 192.168.00.01) to the IP address 1222 (e.g., 192.168.00.02)included in the example request message 1220 and determine that the twoIP addresses do not match (e.g., are not the same or equal).Accordingly, the example wireless zone player 1206 does not request anIP address renewal and the example access point 1202 remains unawarethat the IP address 1212 is leased to a device on the date network 1208.

In contrast, the passive resolver of the wireless zone player 1207 maydetermine that duplicate IP addresses do exist. For example, thewireless zone player 1207 may compare its IP address 1212 (e.g.,192.168.00.02) to the IP address 1222 (e.g., 192.168.00.02) anddetermine that the two IP addresses match (e.g., are the same or equal).Accordingly, the example wireless zone player 1207 initiates an IPaddress renewal, which results in the wireless zone player 1207 losingits IP address when the access point 1202 unicasts or broadcasts anegative acknowledgement message to the wireless zone player 1207. As aresult, the example wireless zone player 1207 initiates a new bindingprocess 1224, which includes an IP address lease request 1226 with an IPaddress 1228 (e.g., 192.168.00.14).

In the illustrated example of FIG. 12b , the example IP AddressConfiguration 1230 is representative of the state of the data network1208 after the access point 1202 leases the IP address 1228 to thewireless zone player 1207. For example, the IP Address Configuration1230 includes that the IP address 1222 is leased to the wired zoneplayer 1204, that the IP address 1212 is not leased to a device on thedata network 1208, and that the IP address 1228 is leased to thewireless zone player 1207. Thus, in the illustrated examples of FIGS.12a and 12b , the wireless zone player 1207 passively facilitatedresolution of an IP address conflict in the data network 1208 bymonitoring messages sent to the access point 1202 and requesting an IPaddress renewal when an IP address included in a message sent to theaccess point 1202 matched the IP address of the zone player 1207.

FIG. 13 shows an illustrative flowchart for another example method 1300to facilitate resolution of IP address conflicts, in accordance with atleast some embodiments described herein. For example, the example method1300 may use the example active resolver 426 to facilitate resolution ofIP address conflicts. The example method 1300 of FIG. 13 begins at block1302 when the example active resolver 426 (FIGS. 4 and/or 10) monitorsthe power status of a wired link of the zone player 400 (FIG. 4). Forexample, the wired interface monitor 1002 (FIG. 10) may monitor the eth0status of the wired interface 406 (FIG. 4). At block 1304, the exampleactive resolver 426 determines whether a detected power status change isindicative of an access point reboot. For example, the wired interfacemonitor 1002 may determine whether the eth0 status changes from a powerOFF state to a power ON state. If, at block 1304, the wired interfacemonitor 1002 determines that the detected power status change is notindicative of an access point reboot, then control proceeds to block1310 to send a probe message.

Otherwise, if, at block 1304, the wired interface monitor 1002determines that the detected power status change is indicative of anaccess point reboot, then, at block 1306, the active resolver 426requests an IP address lease renewal. For example, the example wiredinterface monitor 1002 may initiate the example IP leaser 428 (FIG. 4)to initiate an IP address renew request. At block 1308, the exampleactive resolver 426 generates a probe message indicative of the detectedaccess point reboot. For example, the example message generator 1004(FIG. 10) may generate a probe message including a set renew IP flag,the MAC address of the zone player 400, a message identifier, and a setor reset forwarding flag. At block 1310, the example active resolver 426broadcasts a probe message. For example, the message generator 1004 maybroadcast the probe message generator at block 1308. Alternatively, if,at block 1304, the wired interface monitor 1002 did not detect an accesspoint reboot, then, at block 1310, the example message generator 1004may broadcast a previously obtained probe message. For example, themessage generator 1004 may forward a probe message that includes a setforwarding flag. At block 1312, the example active resolver 426determines whether to continue monitoring for IP address conflicts. Ifthe active resolver 426 determines to continue monitoring for IP addressconflicts, control returns to block 1302 to monitor the wired interfacepower status. Otherwise, if, at block 1312, the active resolver 426determines not to continue monitoring for IP address conflicts (e.g.,due to an application/process shutdown event, a hardware shutdown event,etc.), the example method of FIG. 13 ends.

FIG. 14 shows an illustrative flowchart for another example method 1400to facilitate resolution of IP address conflicts, in accordance with atleast some embodiments described herein. For example, the example method1400 may use the example active resolver 426 to facilitate resolution ofIP address conflicts. The example method 1400 of FIG. 14 begins at block1402 when the example active resolver 426 (FIGS. 4 and/or 10) obtains aprobe message. For example, the probe handler 1006 (FIG. 10) may obtaina probe message from another zone player on the data network 128 (FIG.1). At block 1404, the example active resolver 426 determines whetherthe probe message includes a set renew IP flag. For example, the probehandler 1006 may parse the obtained probe message to check the status ofthe renew IP flag. If, at block 1404, the probe handler 1006 determinesthat the renew IP flag is not set, then control proceeds to block 1410to determine whether the probe message includes a set forwarding flag.

Otherwise, if, at block 1404, the probe handler 1006 determines that theprobe message does include a set renew IP flag, then, at block 1406, theexample active resolver 426 determines whether the probe message is anew probe message. For example, the renew handler 1008 (FIG. 10) maycompare the message identifier of the probe message to previouslyobtained message identifiers retrieved from the example database 430(FIG. 4). If, at block 1406, the example renew handler 1008 determinesthat the obtained probe message is not a new probe message (e.g., theobtained probe message identifier matches a message identifier retrievedfrom the database 430), then control proceeds to block 1410 to determinewhether the probe message includes a set forwarding flag.

Otherwise, if, at block 1406, the renew handler 1008 determines that theobtained probe message is a new probe message (e.g., the obtained probemessage identifier does not match a message identifier retrieved fromthe database 430), then, at block 1408, the example active resolver 426requests a new IP address. For example, the renew handler 1008 mayinitiate the example IP leaser 428 (FIG. 4) to request an IP addresslease renewal.

Regardless of whether the probe handler 1002 determines that theobtained probe message included a reset renew IP flag at block 1404, orthe renew handler 1008 initiates an IP address lease renewal at block1408, at block 1410, the example active resolver 426 determines whetherthe probe message forwarding flag is set. For example, the probe handler1006 may parse the probe message obtained at block 1402 to check thestatus of the forwarding flag. If, at block 1410, the probe handler 1006determines that the forwarding flag is not set, then control proceeds toblock 1414 to determine whether to continue monitoring for IP addressconflicts.

Otherwise, if, at block 1410, the probe handler 1006 determines that theforwarding flag is set, then, at block 1412, the active resolver 426forwards the obtained probe message. For example, the message generator1004 may broadcast the content of the obtained probe message (e.g.,whether the renew IP flag is set or reset, etc.) to other zone playerson the data network 128. At block 1414, the example active resolver 426determines whether to continue monitoring for IP address conflicts. Ifthe active resolver 426 determines to continue monitoring for IP addressconflicts, control returns to block 1402 to obtain a new probe message.Otherwise, if, at block 1414, the active resolver 426 determines not tocontinue monitoring for IP address conflicts (e.g., due to anapplication/process shutdown event, a hardware shutdown event, etc.),the example method of FIG. 14 ends.

As an illustrative example, FIGS. 15a and 15b show example flow pathsfor resolving IP address conflicts in an example environment 1500 suchas the example media system configuration 100 (FIG. 1). The exampleenvironment 1500 includes an example access point 1502 (e.g., a wiredand/or wireless router), an example wired zone player 1504, and examplewireless zone players 1506, 1507. The example access point 1502, theexample wired zone player 1504 and the example wireless zone players1506, 1507 are in communication via an example data network 1508. Theexample wired zone player 1504 is in communication with the exampleaccess point 1502 via a wired interface (e.g., the example wiredinterface 406 (FIG. 4)). The example wireless zone players 1506, 1507are in communication with the example access point 1502 via a wirelessinterface (e.g., the example wireless interface 404 (FIG. 4)).

FIG. 15a is representative of the state of the example environment 1500before an access point reboot is detected. In the illustrated example ofFIG. 12a , the wired zone player 1504 is leasing an IP address 1510(e.g., 192.168.00.01) from the access point 1502, the example wirelesszone player 1506 is leasing an IP address 1511 (e.g., 192.168.00.12)from the access point 1502, and the example wireless zone player 1507 isleasing an IP address 1512 (e.g., 192.168.00.04) from the access point1502. The example wired zone player 1504 periodically (e.g., every 500milliseconds) broadcasts a probe message 1514 over the data network1508. In the illustrated example, the probe message 1514 is obtained bythe wireless zone players 1506, 1507, and the probe message 1514includes a MAC address identifier 1515 (e.g., 01:23:45:67:89:ab), amessage identifier 1516 (e.g., 0013), a renew IP flag 1517 (e.g., zero),and a forwarding flag 1518 (e.g., one). The example MAC addressidentifier 1515 identifies the zone player that generated the probemessage (e.g., the wired zone player 1504). The example messageidentifier 1516 is a locally generated identifier (e.g., generated bythe example message generator 1004 (FIG. 10) of the zone playergenerating the probe message). For example, the message identifier 1516may be a 16-bit alphanumeric identifier. The example renew IP flag 1517is indicative of whether a receiving zone player is to renew its IPaddress lease. In the illustrated example of FIG. 15a , a probe handler1006 (FIG. 10) of the wireless zone player 1506 may parse the obtainedprobe message 1514 and determine that the wireless zone player 1506 isnot to renew its IP address lease with the access point 1502. Theexample forwarding flag 1518 is indicative of whether a receiving zoneplayer is to forward the content of the probe message to other zoneplayers on the data network 1508. For example, the wireless zone player1507 may parse the obtained probe message 1514 (e.g., via the probehandler 1006) and determine not to forward (e.g., broadcast) the contentof the probe message 1514 over the data network 1508 to other zoneplayers.

FIG. 15b is representative of the state of the example environment 1500after the example wired zone player 1504 detects an access point reboot.For example, the eth0 status of the wired interface 406 (FIG. 4) of thewired zone player 1504 may change from a power ON state to a power OFFstate and back to a power ON state. In response to the detected rebootof the example access point 1502, the example wired zone player 1504broadcasts an IP address renewal request and subsequently initiates anew binding process 1519 (e.g., in response to a negativeacknowledgement from the access point 1502).

In addition to initiating the new binding process 1519, the examplewired zone player 1504 generates a new probe message 1522 that isbroadcast over the data network 1508. The example probe message 1522includes a MAC address identifier 1521 (e.g., 01:23:45:67:89:ab), amessage identifier 1522 (e.g., 0014), a renew IP flag 1523 (e.g., one),and a forwarding flag 1524 (e.g., one). The example MAC addressidentifier of the probe message 1514 and the probe message 1520 are thesame as both probe messages 1514, 1520 are generated by the same zoneplayer. The different message identifier 1522 of the probe message 1520indicates that the probe message 1520 is different from the probemessage 1514, and, as a result, the renew IP flag of the probe message1520 is processed rather than discarded. The renew IP flag 1523 of theprobe message 1520 is set (e.g., one) and causes receiving zone playersof the probe message 1520 to request IP address lease renewals. Forexample, the wireless zone player 1506 initiates an IP address leaserenewal request 1526 and the wireless zone player 1507 initiates an IPaddress lease renewal request 1527 in response to processing theobtained probe message 1520.

In the illustrated example of FIG. 15b , the example forwarding flag1524 is set (e.g., one). Thus, in response to the wireless zone players1506, 1507 obtaining the probe message 1520, each respective wirelesszone player generates a probe message including the content of the probemessage 1520. For example, the wireless zone player 1506 generates aprobe message 1528 that is broadcast over the data network 1508. In theillustrated example, the probe message 1528 of FIG. 15b includes a MACaddress identifier 1529 (e.g., 01:23:45:67:89:ab) that is the same asthe MAC address identifier 1521 of the probe message 1520, a messageidentifier 1530 (e.g., 0014) that is the same as the message identifier1522 of the probe message 1520, a renew IP flag 1531 (e.g., one) that isthe same as the renew IP flag 1523 of the probe message 1520, and aforwarding flag 1532 that is the same as the forwarding flag 1524 of theprobe message 1520. In some examples, the forwarding flag 1532 may bedifferent than the forwarding flag 1524. For example, the wireless zoneplayer 1506 may include a state variable that determines whether a zoneplayer is to forward probe messages.

Thus, in the illustrated examples of FIGS. 15a and 15b , the zoneplayers 1504, 1506, 1507 of the environment 1500 actively facilitateresolution of IP address conflicts in the data network 1508 by causingother zone players to request an IP address lease renewal in response todetecting an access point reboot on the data network 1508.

IX. Conclusion

The descriptions above disclose various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

As suggested above, the present application involves resolving IPaddress conflicts. In one aspect, a first method is provided. The firstmethod involves listening, by a first playback device having a firstInternet Protocol (IP) address, to a specified server port. The firstmethod also includes receiving, by the first playback device from asecond playback device via the specified server port, a message, whereinthe message identifies a second IP address, wherein the second IPaddress has been assigned to the second playback device. The firstmethod also includes determining, by the first playback device, whetherthe first IP address is the same as the second IP address. The firstmethod also includes, when the first IP address is the same as thesecond IP address, obtaining, by the first playback device, a new IPaddress, wherein the new IP address is different from the first IPaddress and the second IP address.

In another aspect, a second method is provided. The second methodinvolves a network comprising at least a playback device and an accesspoint, wherein there is a connection via a wire between the access pointand the playback device. The second method includes periodicallybroadcast, by the playback device over the network, a probe message. Thesecond method also includes detecting, by the playback device, a changein status associated with the connection. The second method alsoincludes, based on the detection, obtaining, by the playback device, anew Internet Protocol (IP) address. The second method also includes,based on the detection, including, by the playback device in at leastone probe message broadcast subsequent to the detection, an indicationthat other playback devices on the network should obtain a new IPaddress.

In a further aspect, a first non-transitory computer readable mediumhaving instructions stored thereon is provided. The instructions areexecutable by a first playback device having a first Internet Protocol(IP) address to cause the first playback device to perform functionsincluding listening to a specified server port. The instructions alsocause the first playback device to receive from a second playback devicevia the specified server port, a message, wherein the message identifiesa second IP address, wherein the second IP address has been assigned tothe second playback device. The instructions are also cause the firstplayback device to determine whether the first IP address is the same asthe second IP address. The instructions are also cause the firstplayback device to, when the first IP address is the same as the secondIP address, obtain a new IP address, wherein the new IP address isdifferent from the first IP address and the second IP address.

In yet another aspect, a second non-transitory computer readable mediumhaving instructions stored thereon is provided. The instructions areexecutable by a playback device to cause the playback device to performfunctions including periodically broadcasting a probe message over anetwork. The instructions also cause the playback device to detect achange in status associated with a wired connection to the playbackdevice. The instructions also cause the playback device to, based on thedetection, obtain a new Internet Protocol (IP) address. The instructionsalso cause the playback device to, based on the detection, include in atleast one probe message broadcast subsequent to the detection, anindication that other playback devices on the network should obtain anew IP address.

In yet another aspect, a first system involves a playback deviceincluding a network interface, a processor, data storage, and programlogic stored in the data storage and executable by the processor tolisten to a specified server port via the network interface. The programlogic to also cause the processor to receive from a second playbackdevice via the specified server port, a message, wherein the messageidentifies a second Internet Protocol (IP) address, wherein the secondIP address has been assigned to the second playback device. The programlogic to also cause the processor to determine whether a first IPaddress assigned to the playback device is the same as the second IPaddress. The program logic to also cause the processor to, when thefirst IP address is the same as the second IP address, obtain a new IPaddress, wherein the new IP address is different from the first IPaddress and the second IP address.

In yet another aspect, a second system involves a playback deviceincluding a network interface, a processor, data storage, and programlogic stored in the data storage and executable by the processor toperiodically broadcast a probe message over a network. The program logicto also cause the processor to detect a change in status associated witha wired connection to the playback device. The program logic to alsocause the processor to, based on the detection, obtain a new InternetProtocol (IP) address. The program logic to also cause the processor to,based on the detection, include in at least one probe message broadcastsubsequent to the detection, an indication that other playback deviceson the network should obtain a new IP address.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

The example processes of FIGS. 11, 13 and/or 14 may be implemented usingcoded instructions (e.g., computer and/or machine readable instructions)stored on a tangible computer readable storage medium such as a harddisk drive, a flash memory, a read-only memory (ROM), a compact disk(CD), a digital versatile disk (DVD), a cache, a random-access memory(RAM) and/or any other storage device or storage disk in whichinformation is stored for any duration (e.g., for extended time periods,permanently, for brief instances, for temporarily buffering, and/or forcaching of the information). As used herein, the term tangible computerreadable storage medium is expressly defined to include any type ofcomputer readable storage device and/or storage disk and to excludepropagating signals and to exclude transmission media. As used herein,“tangible computer readable storage medium” and “tangible machinereadable storage medium” are used interchangeably. Additionally oralternatively, the example processes of FIGS. 11, 13 and/or 14 may beimplemented using coded instructions (e.g., computer and/or machinereadable instructions) stored on a non-transitory computer and/ormachine readable medium such as a hard disk drive, a flash memory, aread-only memory, a compact disk, a digital versatile disk, a cache, arandom-access memory and/or any other storage device or storage disk inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, for brief instances, for temporarily buffering,and/or for caching of the information). As used herein, the termnon-transitory computer readable medium is expressly defined to includeany type of computer readable storage device and/or storage disk and toexclude propagating signals and to exclude transmission media. As usedherein, when the phrase “at least” is used as the transition term in apreamble of a claim, it is open-ended in the same manner as the term“comprising” is open ended.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

We claim:
 1. A method comprising: determining, by a first audio playbackdevice, that a message sent by a second audio playback device to aspecified server port includes a first lease renew request of the secondaudio playback device, wherein the first audio playback device isassigned a first Internet Protocol (IP) address, wherein the first IPaddress was assigned by a host device; and wherein a zone groupcomprises the first audio playback device and the second audio playbackdevice; determining, by the first audio playback device, that the firstIP address of the first audio playback device is the same as a second IPaddress identified in the first lease renew request of the second audioplayback device; in response to determining that the first IP address ofthe first audio playback device is the same as the second IP addressidentified in the first lease renew request of the second audio playbackdevice, obtaining, by the first audio playback device from the hostdevice, a new IP address by sending a second lease renew request to thespecified server port, wherein the new IP address is different from thefirst IP address and the second IP address; after obtaining the new IPaddress, receiving, by the first audio playback device, a stream ofaudio content; sending, by the first audio playback device, the audiocontent to the second audio playback device; and playing, by the firstaudio playback device, audio based on the audio content in synchronywith the zone group.
 2. The method of claim 1, wherein the specifiedserver port comprises UDP port
 67. 3. The method of claim 1, wherein thefirst lease renew request is a DHCP_REQUEST packet.
 4. The method ofclaim 3, wherein the DHCP_REQUEST packet includes an options field, andwherein the options field identifies the second IP address.
 5. Themethod of claim 1, wherein the host device is a DHCP server; and whereinobtaining the new IP address comprises: transmitting, by the first audioplayback device to the DHCP server, a DHCP request, wherein the secondlease renew request comprises the DCHP request; and receiving, by thefirst audio playback device from the DHCP server, a DHCPacknowledgement, wherein the DHCP acknowledgement includes the new IPaddress.
 6. The method of claim 5, wherein the first audio playbackdevice comprises a first zone player, and wherein the second audioplayback device comprises a second zone player.
 7. The method of claim6, wherein the DHCP server comprises an access point.
 8. The method ofclaim 1, wherein the specified server port is an input port to the hostdevice.
 9. A non-transitory computer-readable storage medium including aset of instructions for execution by a processor, the set ofinstructions, when executed, cause a first playback device having afirst Internet Protocol (IP) address to: determine, by a first audioplayback device, that a message sent by a second audio playback deviceto a specified server port includes a first lease renew request of thesecond audio playback device, wherein the first audio playback device isassigned a first Internet Protocol (IP) address, wherein the first IPaddress was assigned by a host device; and wherein a zone groupcomprises the first audio playback device and the second audio playbackdevice; determine that the first IP address of the first audio playbackdevice is the same as a second IP address identified in the first leaserenew request of the second audio playback device; in response todetermining that the first IP address of the first audio playback deviceis the same as the second IP address identified in the first lease renewrequest of the second audio playback device, obtain a new IP addressfrom the host device by sending a second lease renew request to thespecified server port, wherein the new IP address is different from thefirst IP address and the second IP address; after obtaining the new IPaddress, receive, by the first audio playback device, a stream of audiocontent; send, by the first audio playback device, the audio content tothe second audio playback device; and play, by the first audio playbackdevice, audio based on the audio content in synchrony with the zonegroup.
 10. The computer-readable medium of claim 9, wherein thespecified server port comprises UDP port
 67. 11. The computer-readablemedium of claim 9, wherein the first lease renew request is aDHCP_REQUEST packet.
 12. The computer-readable medium of claim 11,wherein the DHCP_REQUEST packet includes an options field, and whereinthe options field identifies the second IP address.
 13. Thecomputer-readable medium of claim 9, wherein the host device is a DHCPserver; and wherein obtaining the new IP address comprises instructionsthat when executed cause the first playback device to: transmit to theDHCP server, a DHCP request; wherein the second lease renew requestcomprises the DCHP request; and receive from the DHCP server, a DHCPacknowledgement, wherein the DHCP acknowledgement includes the new IPaddress.
 14. The computer-readable medium of claim 13, wherein the firstaudio playback device comprises a first zone player, and wherein thesecond audio playback device comprises a second zone player.
 15. Thecomputer-readable medium of claim 14, wherein the DHCP server comprisesan access point.
 16. A first audio playback device comprising: a networkinterface; a processor; data storage; and program logic stored in thedata storage and executable by the processor to: determine, by the firstaudio playback device, that a message sent by a second audio playbackdevice to a specified server port includes a first lease renew requestof the second audio playback device, wherein the first audio playbackdevice is assigned a first Internet Protocol (IP) address, wherein thefirst IP address was assigned by a host device; and wherein a zone groupcomprises the first audio playback device and the second audio playbackdevice; determine that a first IP address assigned to the first audioplayback device is the same as a second IP address identified in thefirst lease renew request of the second audio playback device; inresponse to determining that the first IP address of the first audioplayback device is the same as the second IP address identified in thefirst lease renew request of the second audio playback device, obtain anew IP address from the host device by sending a second lease renewrequest to the specified server port, wherein the new IP address isdifferent from the first IP address and the second IP address; afterobtaining the new IP address, receive, by the first audio playbackdevice, a stream of audio content; send, by the first audio playbackdevice, the audio content to the second audio playback device; and play,by the first audio playback device, audio based on the audio content insynchrony with the zone group.
 17. The first audio playback device ofclaim 16, wherein the specified server port comprises UDP port
 67. 18.The first audio playback device of claim 16, wherein the first leaserenew request is a DHCP_REQUEST packet.
 19. The first audio playbackdevice of claim 18, wherein the DHCP_REQUEST packet includes an optionsfield, and wherein the options field identifies the second IP address.20. The first audio playback device of claim 16, wherein the host deviceis a DHCP server; and wherein obtaining the new IP address comprisesprogram logic stored in the data storage that when executed cause thefirst playback device to: transmit to the DHCP server, a DHCP requestwherein the second lease renew request comprises the DCHP request; andreceive from the DHCP server, a DHCP acknowledgement, wherein the DHCPacknowledgement includes the new IP address.
 21. The first audioplayback device of claim 20, wherein (i) the first audio playback devicecomprises a first zone player, and (ii) the second audio playback devicecomprises a second zone player.
 22. The non-transitory computer-readablestorage medium of claim 9, wherein the specified server port is an inputport to the host device.
 23. The first audio playback device of claim16, wherein the specified server port is an input port to the hostdevice.